Necessarily picks up dodal 1.54 for the adsim module to be able to use
the PathProvider that we want to, and ophyd-async 0.12.1 for a bug fix
in the ADHDFWriter

---------

Co-authored-by: Callum Forrester <[email protected]>

The example-services compose-file that we for our system tests is
[adjusting the ports that it
uses](epics-containers/example-services#43). As
we are tracking main of that repository we need to pin this dependency,
allowing the ports to be adjusted for the next release.

With Renovate we should be able to keep the dependency pinned and use
the latest releases, which will require an adjustment to the ports when
the release is made.

The Renovate config in this repository needs migrating. Typically this
is because one or more configuration options you are using have been
renamed.

You don't need to merge this PR right away, because Renovate will
continue to migrate these fields internally each time it runs. But later
some of these fields may be fully deprecated and the migrations removed.
So it's a good idea to merge this migration PR soon.





🔕 **Ignore**: Close this PR and you won't be reminded about config
migration again, but one day your current config may no longer be valid.

❓ Got questions? Does something look wrong to you? Please don't hesitate
to [request help
here](https://redirect.github.com/renovatebot/renovate/discussions).


---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/DiamondLightSource/blueapi).

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…python-copier-template to v4.1.0  (#1140)

Fixes #ISSUE

### Instructions to reviewer on how to test:
1. Do thing x
2. Confirm thing y happens

### Checks for reviewer
- [ ] Would the PR title make sense to a user on a set of release notes

…1153)

### Instructions to reviewer on how to test:
1. Pull this branch and verify that `pre-commit` hooks are active.
   Run the following command to confirm `gitleaks` is correctly set up:

   ```
   pre-commit run --all-files
   ```

This should include output from gitleaks, detecting potential hardcoded
secrets.
   
Note: It is assumed that the CI environment handles installing gitleaks
as part of the `pre-commit` configuration.
   For local testing, the following setup was used:

   ```
   python3 -m venv .venv
   source .venv/bin/activate
   pip install pre-commit
   pre-commit install --hook-type pre-commit
   pre-commit run --all-files
   ```

2. Test gitleaks manually by attempting to commit a file containing a
fake secret (e.g., a fake API key or private key).
The commit should be blocked by gitleaks if the secret is detected. Note
that detection may include false positives or occasionally miss some
secrets (false negatives).

For more information, including configuration options for customizing
detection rules, refer to the official documentation:
    https://github.com/gitleaks/gitleaks

Co-authored-by: Joseph Ware <[email protected]>

close #1151

Removes configuration for sonar scanning action that was left by #1092
And tidies the pre-commit action to allow the catalog-info to be checked
for validity in the CI

…osite_devices